fix(webpack): don't use deprecated config with isolatedConfig #14802
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Current Behavior
When running a webpack dev server, the webpack configuration is built with the "old" way by using
withNx
andwithWeb
even thoughisolatedConfig
is set totrue
.The main issue with that is that if a user return an immutable config from one of his plugins together with
withNx
andwithWeb
it will run them twice becauseprocessed
is caching it by reference.The following example will run
withNx
andwithWeb
twice, resulting in duplicated plugins and other invalid configurations:BTW - immutability is anyway an issue with the current tracking.
Expected Behavior
Should respect
isolatedConfig
in dev server tooRelated Issue(s)
Fixes #